Project-Env is a small, engineering-focused publisher that streamlines toolchain management for Java, Kotlin, Scala, Node, Python, Go and other polyglot code bases. Instead of asking every contributor to install the right compiler, formatter, linter or SDK by hand, teams commit a single project-env.toml file to the repository; the Project-Env CLI reads that manifest and downloads, unpacks and wires the declared versions into an isolated project-specific directory tree. Because the CLI is headless and written in native Go, it runs identically on Windows, macOS and Linux build agents, making CI pipelines and developer laptops behave the same. Complementing the CLI, the optional Project-Env Shell utility injects those managed tools into the interactive command line: typing mvn, npm, python or java automatically resolves to the exact build declared in the configuration, eliminating “works on my machine” drift without touching the operating-system PATH. Typical use cases include onboarding a new hire in minutes, switching between branches that need different Java or Node releases, or auditing which tool versions were used to produce a given artifact. Both components are open source, MIT-licensed and distributed as single self-contained executables. Project-Env software is available free of charge on get.nero.com, where downloads are delivered through trusted Windows package sources such as winget, always resolve to the newest upstream release, and can be queued for batch installation alongside other applications.

Project-Env CLI

The Project-Env CLI represents the raw core of Project-Env which allows the setup of tools based on a project-env.toml configuration file and therefore the integration of Project-Env into an existing environment.

Details
Project-Env Shell

The Project-Env Shell integration application allows to use tools setup by the Project-Env CLI in a shell environment.

Details